Transportable private cloud computing platform and associated method of use

ABSTRACT

The present invention is a transportable private cloud computing platform, having a rack, several servers, a system management server, an interface device, a network switch, a power supply circuit, and a transit case. The present invention also includes a method for initializing the transportable private cloud computing platform, and a method for migrating software applications to the transportable private cloud computing platform.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a divisional of prior U.S. patent application Ser.No. 13/360,157, filed Jan. 27, 2012, which is hereby incorporated hereinby reference in its entirety.

FIELD OF INVENTION

The present invention relates generally to cloud computing, and inparticular to system administrator assisted creation, operation, andmanagement of a private cloud on a transportable private cloud computingplatform.

BACKGROUND OF THE INVENTION

Cloud computing is the delivery of computing as a service rather than aproduct, whereby resources, software, and information are provided tocomputers and other devices as a utility over a network. Typically,cloud computing services are offered by cloud computing serviceproviders on a pay-per-usage basis. Cloud computing has evolved intomultiple deployment models, including public clouds, community clouds,and private clouds. A “public cloud” is a model where a service providermakes resources, such as software applications and storage, available tothe general public. A “community cloud” shares infrastructure betweenseveral organizations from a specific community with common concerns. A“community cloud” may be hosted by a third party or hosted internally orexternally by the specific community. A “private cloud” isinfrastructure operated solely for a single organization or restrictedgroup of users. A “private cloud” may be hosted by a third party orhosted internally or externally by the specific community whethermanaged internally or by a third-party and hosted internally orexternally by the single organization or restricted group of users.

There are a number of challenges associated with relying on a public orcommunity cloud computing environment. First, data governance ishindered by the use of public or community cloud computing providersthat may or may not guarantee the safety and security of data stored inthe provider's cloud. Second, public or community cloud computingproviders lack resource management capabilities which allow a systemadministrator to scale resource utilization based on server load andsoftware application usage. Third, network latency associated with usinga public or community cloud computing environment may make the cloudsluggish and cumbersome. Fourth, system administrators may findthemselves at the mercy of a public or community cloud computingprovider because of poor reliability or low availability. Finally, thereremains the looming issue of security on the virtual servers that makeup the public or community environments. For these reasons, a systemadministrator is well-advised to seek a private cloud solution in anattempt to overcome some or all of these challenges associated withrelying on a public or community cloud computing environment.

The creation of a private cloud solution requires a knowledge set notnormally available to the average system administrator. Theimplementation process may be a timely and frustrating process repletewith opportunities for making mistakes or introduction of errors, whichwill terminate the process or lead to a less that optimal cloudinstance. For these reasons, a method of initializing a transportableprivate cloud computing platform is desirable.

Once a private cloud solution has been created, system administratorsneed the capability of migrating software applications to the cloud inorder to make use of the available cloud resources. Traditionally, asystem administrator takes inventory of local software applications andselects candidates for migration to the cloud. For these reasons, amethod of migrating software applications to a transportable privatecloud computing platform is desirable.

A typical cloud computing environment is established within the confinesof a server room, data warehouse, or other similar physical structurewithin a cloud computing facility. In the event of a natural disaster,these cloud computing environments are vulnerable to degradedperformance and even total loss. It is common practice for a host of acloud computing environment to engage in contingency planning, which mayconsist of full-scale disaster recovery, failover capabilities, andsystem redundancy. A problem with this type of planning is therequirement of a full-scale or nearly full-scale replica of the cloudcomputing environment in a different location. A mobile cloud computingplatform is desirable to reduce or eliminate the need for a full-scalereplica of a cloud computing environment in case of natural disaster orother interruption of service at the primary cloud computing facility.In the event of an imminent natural disaster, the mobile cloud computingplatform may be relocated to avoid an interruption in service.

It may also be desirable to create a cloud computing environment in aremote or inhospitable location. Traditional cloud computing serviceproviders would be inadequate due to lack of network connectivity andnetwork latency. A mobile cloud computing platform could be deployed tosuch a location and a private cloud environment could be instantiated toprovide cloud services to a limited geographic area.

The present invention is directed to overcoming one or more of theproblems set forth above.

SUMMARY OF THE INVENTION

This section provides a general summary of the disclosure, and is not acomprehensive disclosure of its full scope or all of its features. Thepresent invention is directed at a transportable private cloud computingplatform.

An aspect of this invention provides a transportable private cloudcomputing platform, that includes at least one rack with sufficientstorage capacity to hold hardware components necessary to run a privatecloud instance, at least two servers mounted on the rack that arecapable of hosting private cloud operating systems, softwareapplications and data storage, wherein the at least one of the at leasttwo servers includes a system management server that utilizes systemmanagement software for managing the physical resources, the virtualserver instances, and the software, an interface device that allows asystem administrator to interact with the private cloud instance and theinterface device provides guidance to the system administrator to createand administer a fully configured and operational private cloud that isconnected to the at least two servers, at least one network switchmounted on the rack, and a power supply circuit capable of distributingpower to the at least two servers, the interface device and the at leastone network switch.

Another aspect of this invention provides a method of initializing atransportable private cloud computing platform, which includes applyingpower to a power supply circuit of a transportable private cloudcomputing platform, which also includes a rack, an interface device, atleast two servers, at least one cloud computing operating system, and atleast one network switch, activating a graphical user interface on theinterface device, utilizing the interface device to provide queries tothe system administrator so that a particular cloud computing operatingsystem may be selected from the at least one cloud computing operatingsystems, starting the selected cloud computing operating system thatoperates as a private cloud, utilizing the interface device to requestrequired keys from a system administrator, initiating a cloud operatingsystem virtualizer, utilizing the interface device to allow a systemadministrator to enter the IP range of addresses, each of the IPaddresses representing one of the at least two servers, to be integratedinto the private cloud, locating and initializing, if not alreadyinitialized, each system administrator-selected server with the selectedcloud computing operating system, incorporating the physical resourcesof each server of the at least two servers into the private cloud,utilizing the interface device to provide queries to the systemadministrator so that virtual server information is entered, and thencreating the virtual servers.

Another aspect of this invention provides a method of migrating softwareapplications to a transportable private cloud computing platform, whichincludes utilizing an interface device to allow a system administratorto invoke a software application migration system, searching forsoftware applications that are available to be migrated to the privatecloud computing platform, presenting a list of software applicationsthat are available to be migrated to the private cloud computingplatform, selecting an software application from the list of softwareapplications that are available to be migrated to the private cloudcomputing platform, the selected software application becoming themigrating software application, resourcing the correct virtual serverconfiguration on the private cloud computing platform to accommodate themigrating software application, migrating the software application tothe private cloud computing platform; and migrating any softwareapplication data of the migrating software application to the privatecloud computing platform, where the private cloud computing platform istransportable.

These are merely some of the innumerable aspects of the presentinvention and should not be deemed an all-inclusive listing of theinnumerable aspects associated with the present invention. These andother aspects will become apparent to those skilled in the art in lightof the following disclosure and accompanying drawings. The descriptionand specific examples in this summary are intended for purposes ofillustration only and are not intended to limit the scope of the presentdisclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawings described herein are for illustrative purposes only ofselected embodiments and not all possible implementations, and are notintended to limit the scope of the present disclosure. For a betterunderstanding of the present invention, reference may be made to theaccompanying drawings in which:

FIG. 1 is a front elevational view of a preferred illustrative, butnonlimiting, embodiment of a transportable private cloud computingplatform in accordance with the present invention;

FIG. 2 shows multiple views of preferred illustrative, but nonlimiting,embodiments of a transportable private cloud computing platform inaccordance with the present invention;

FIG. 3 shows two different rack sizes for a transportable private cloudcomputing platform in accordance with the present invention;

FIG. 4 shows two adjoining racks in one transportable private cloudcomputing platform in accordance with the present invention;

FIG. 5 shows an interface device in accordance with the presentinvention;

FIG. 6 shows several transit cases in accordance with the presentinvention;

FIG. 7 shows a stand-alone transportable private cloud computingplatform in accordance with the present invention;

FIG. 8 shows a mobility mechanism in accordance with the presentinvention;

FIG. 9 shows a resizable removably attached transit case accordance withthe present invention;

FIG. 10 shows various combinations of private cloud instances andtransportable private cloud computing platforms in accordance with thepresent invention;

FIG. 11 shows a transportable private cloud computing platform with awireless network and connected to a public cloud in accordance with thepresent invention;

FIG. 12 shows a table with representative software components of atransportable private cloud computing platform in accordance with thepresent invention;

FIG. 13 shows a flow diagram of a private cloud initialization processin accordance with the present invention;

FIG. 14 shows a flow diagram of a private cloud software applicationmigration process in accordance with the present invention; and

FIG. 15 shows a flow diagram of a private cloud combined sequentialprocess in accordance with the present invention.

Reference characters in the written specification indicate correspondingitems shown throughout the drawing figures.

DETAILED DESCRIPTION OF THE INVENTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of the invention.However, it will be understood by those skilled in the art that thepresent invention may be practiced without these specific details. Inother instances, well-known methods, procedures, and components, e.g.,devices, have not been described in detail so as to obscure the presentinvention.

The following list of definitions are provided in order to ensure aconsistent understanding of terms used throughout this disclosure: a“system administrator” is a person who interfaces with the transportableprivate cloud computing platform to instantiate and configure a privatecloud computing environment as well as manage and maintain the resourcesof the private cloud; a “user” is a person or entity that connects tothe transportable private cloud computing platform and utilize cloudcomputing resources; “ruggedized” means that the unit is designed withprotection against rough use or rough environments; and “transportable”means movable as a singular unit.

An illustrative, but nonlimiting, embodiment of a transportable privatecloud computing platform in accordance with the principles of thisinvention is indicated generally as 100 in FIG. 1. The transportableprivate cloud computing platform 100 has at least one rack 101 withsufficient storage capacity to hold the hardware components or devicesnecessary to run a private cloud instance, as described below. In theillustrative, but nonlimiting, embodiment shown in FIG. 1, the at leastone rack 101 is a sixteen (16) RU rack. The at least one rack 101 ismounted in a removably attached transit case 108. The transportableprivate cloud computing platform 100 has a plurality of servers 102mounted on the at least one rack 101 and capable of hosting privatecloud operating systems, software applications and data storage.

In the illustrative, but nonlimiting, embodiment shown in FIG. 1, theplurality of servers 102 is comprised of six (6) servers. Five (5) ofthe plurality of servers 102 are 2 U x86 servers 103 with dual socketmotherboards. Each of the 2 U x86 servers 103 has two (2) CPUs with aminimum of twelve (12) cores, a minimum of One Hundred and Twenty-eight(128) Gigabyte (GB) of memory, at least eight (8) terabyte (TB) ofattached storage, and at least two (2) Bb Network Interface Cards(NICs). In the transportable private cloud computing platform 100, atleast one of a number of servers 102 is a system management server 104that utilizes system management software for managing any physicalresources, any virtual server instances, and any software applicationsof the transportable private cloud computing platform 100. In theillustrative, but nonlimiting, embodiment shown in FIG. 1, a systemmanagement server 104 is a 1 U server with a single two-core CPU, atleast eight gigabyte (GB) of memory, at least 500 gigabyte (GB) ofstorage and at least two one (1) gigabyte (Gb) Network Interface Cards(NICs).

The transportable private cloud computing platform 100 has an interfacedevice 105 mounted on the at least one rack 101 that allows a systemadministrator to interact with the private cloud instance and theinterface device provides guidance to the system administrator to createand administer a fully configured and operational private cloud. Theinterface device 105 may also be referred to as an “interface component”in some embodiments. In the illustrative, but nonlimiting, embodimentshown in FIG. 1, the interface device 105 has a combination keyboard,video, and mouse (KVM) switch which is used, in conjunction with anattached keyboard, video, and mouse, to facilitate input and outputbetween the transportable private cloud computing platform 100 and asystem administrator via a graphical user interface (GUI). Thetransportable private cloud computing platform 100 has at least onenetwork switch 106 mounted on the at least one rack 101. In theillustrative, but nonlimiting, embodiment shown in FIG. 1, the at leastone network switch 106 may include two twelve (12) port or twenty-four(24) port Gigabit Ethernet Switches with 10 Gigabit up-links. Thetransportable private cloud computing platform 100 has a power supplycircuit 107 capable of distributing power to the components of theprivate cloud. In the illustrative, but nonlimiting, embodiment shown inFIG. 1, the power supply circuit 107 is a UPS.

A key aspect of the transportable private cloud computing platform 100is that all of the enumerated components and/or devices necessary tocreate a private cloud instance are bundled into a singular unit, andthat singular unit is transportable. The “transportable” aspect of thetransportable private cloud computing platform 100 is that it be movableas a singular unit. For example, it is not necessary to strip thecomponents and/or devices from the at least one rack 101 or remove therack from the removably attached transit case 108 before moving thetransportable private cloud computing platform 100.

The transportable private cloud computing platform 100 may take on manyforms and configurations. The prime mover of the transportable privatecloud computing platform 100 may vary as shown in FIG. 2. FIG. 2 showsseveral different preferred illustrative, but nonlimiting, embodimentsof the transportable private cloud computing platform 100. The desktoptransportable private cloud computing platform 201 is sufficiently smalland lightweight that a person could transport it. The rack transportableprivate cloud computing platform 202 has much greater capacity than thedesktop transportable private cloud computing platform 201. Theruggedized transportable private cloud computing platform 203 is a moredurable solution designed to withstand outdoor conditions. The modulartransportable private cloud computing platform 204 is designed to bemoved in much the same way that a shipping container would be moved,deployed in an outdoor environment, and fit in a parking space. Themobile transportable private cloud computing platform 205 is designed tobe moved by a transport truck or similar vehicle.

The transportable private cloud computing platform 100 provides one ormore private cloud instances. The transportable private cloud computingplatform 100 provides the infrastructure necessary to operate one ormore private clouds for a single organization or restricted group ofusers. As such, the transportable private cloud computing platform 100will have access controls in place to restrict access to the privatecloud to a limited number of users.

The transportable private cloud computing platform 100 is a computingplatform, meaning that it has the hardware architecture and a softwareframework necessary to instantiate and run at least one private cloudinstance. The specific form of the hardware architecture and softwareframework of a transportable private cloud computing platform 100 mayvary, as described in the following paragraphs.

The rack 101, where there is at least one rack, may take on many forms,as the form of the rack 101, by itself, is not a central feature of thisinvention. In FIG. 1, the rack 101 is a 16 RU rack. The desktoptransportable private cloud computing platform 201 will contain a smallrack, which is a small form-factor rack with enough capacity to host theessential elements of the transportable private cloud computing platform100. The modular transportable private cloud computing platform 204 andmobile transportable private cloud computing platform 205 may contain arack or racks of much greater form factor.

FIG. 3 illustrates a small form factor rack 301 embodied in the desktoptransportable private cloud computing platform 201. A large form factorrack 302 is embodied in the modular transportable private cloudcomputing platform 204. Referring now to FIG. 4, the at least one rack101 is embodied in two large form factor racks 302 staged side-by-sideinside the mobile transportable private cloud computing platform 205. Ifthe at least one rack 101 consists of more than one rack, thearrangement of the racks may vary.

The plurality of servers 102 may take on many forms, as the form of thenumber of servers 102, by themselves, are not a central feature of thisinvention. The only requirement is that the plurality of servers 102 becapable of hosting private cloud operating systems, softwareapplications, and data storage. As private cloud operating systems andsoftware applications continue to evolve, data storage needs continue toincrease, and server technology advances, it is envisioned that theservers making up the plurality of servers 102 will be upgraded orswapped out. The servers making up the plurality of servers 102 willtake on greater processing capacity, greater processing speed, greaterrandom access memory (RAM), greater storage, improved network interfacecards (NICs), and other improvements.

The system management server 104 could be any of the plurality ofservers 102. The system management server 104 provides the cloudmanagement software tools and resources for a system administrator tomanage the resources of the transportable private cloud computingplatform 100.

The interface device 105 may also take on many forms. The interfacedevice 105 is the mechanism by which the system administrator interactswith the transportable private cloud computing platform 100. Theinterface device 105 requires software and physical elements tofacilitate input and output between a system administrator and thetransportable private cloud computing platform 100. The interface device105 shown in FIG. 1 is a KVM, but the particular software used to managevirtual servers may change over time. The interface device 105 has agraphical user interface (GUI), which is intended to providestep-by-step guidance to enable a novice system administrator with nocloud technical experience to initialize, configure, and manage aprivate cloud computing environment. The graphical user interface (GUI)of the interface device 105 may run on any of the plurality of servers102, but most likely it runs on the system management server 104. Inaddition, the system management server 104 may run both systemmanagement software and interface device 105 software. The graphicaluser interface (GUI) for the system management server 104 may be thesame graphical user interface (GUI) that is used for the interfacedevice 105. It is expected that a system administrator will plug in akeyboard, video monitor, and mouse to the interface device 105 as shownin FIG. 5.

The at least one network switch 106 may also take on many forms, as theform of the at least one network switch 106 is not a central feature ofthis invention. It is envisioned that the at least one network switch106 may be upgraded or swapped out at any time better technology isavailable.

The power supply circuit 107 may also take on many forms. In a preferredillustrative, but nonlimiting, embodiment, the power supply circuit 107is an uninterruptable power supply. In another illustrative, butnonlimiting, embodiment, the power supply circuit is standard 110-voltalternating current (AC) circuit fed through a standard power cord. Inanother illustrative, but nonlimiting, embodiment, there are severalredundant 110-volt alternating current (AC) plugs and one of severalredundant rectifier units convert the power to forty-eight (48) voltsdirect current (DC). The direct current (DC) voltage is desirablebecause it is more efficient, increases the reliability of the server,and cuts down on the noise because the fans and heat sinks may beeliminated. In yet another illustrative, but nonlimiting, embodiment,power is supplied by a generator. It is envisioned that anyvoltage-producing source may be used to supply power to thetransportable private cloud computing platform 100.

In any of the illustrative, but nonlimiting, embodiments of thetransportable private cloud computing platform 100, and illustrated inFIG. 2, the transportable private cloud computing platform 100 has aremovably attached transit case 108 over the at least one rack 101 toprotect the interior components. The removably attached transit case 108could be made of any material and be any shape so long as it is capableof protecting the interior components and allowing the transportableprivate cloud computing platform 100 to function properly. The removablyattached transit case 108 may be a hardened transit case. The hardenedtransit case may be made of metal, plastic, or any other hardenedmaterial. In some illustrative, but nonlimiting, embodiments, theremovably attached transit case 108 is waterproof and/orwater-resistant. In some illustrative, but nonlimiting, embodiments, theremovably attached transit case 108 is heat-resistant and/orfire-resistant. The removably attached transit case 108 should cover thetop and sides of the transportable private cloud computing platform 100.The transit case does not necessarily need to cover the front, back, orbottom of the transportable private cloud computing platform 100, thoughit could. The removably attached transit case 108 may be comprised ofseveral components, where all the components and/or devices are attachedto the transportable private cloud computing platform 100 to protect itduring transport. The removably attached transit case 108 may haveopenings for ventilation or for attachment of external components and/ordevices such as a power cord or keyboard.

In FIG. 6, an illustrative, but nonlimiting, embodiment of the removablyattached transit case 108 is a plastic hardened transit case 601. Insome illustrative, but nonlimiting, embodiments, the plastic hardenedtransit case 601 has a removable front cover 602, which may be detachedat any time. In another illustrative, but nonlimiting, embodiment, theremovably attached transit case 108 is a metal hardened transit case603. In some illustrative, but nonlimiting, embodiments, the metalhardened transit case 603 has an entry door 604.

In an illustrative, but nonlimiting, embodiment, the transportableprivate cloud computing platform 100 is ruggedized, as shown in FIG. 2.The ruggedized transportable private cloud computing platform 203 isdesigned specifically to withstand outdoor conditions, but the otherillustrative, but nonlimiting, embodiments shown in FIG. 2 may bemodified to be ruggedized as well. A transportable private cloudcomputing platform 100 that has been ruggedized has some additionalfeature, added as protection, to allow it to withstand rough handling orrough environments. The additional feature added to a transportableprivate cloud computing platform 100 to make it ruggedized may bewaterproofing, water resistance, padding, durable components, or avariety of other features that add protection. In some illustrative, butnonlimiting, embodiments, the additional ruggedizing feature is aplurality of servers 102 that have been modified to withstand impactsand rough handling. In an illustrative, but nonlimiting, embodimentshown in FIG. 6, the transportable private cloud computing platform 100has a plastic hardened transit case 601, which make is ruggedized.

In an illustrative, but nonlimiting, embodiment, the transportableprivate cloud computing platform 100 is a stand-alone unit. A“stand-alone unit” means that the transportable private cloud computingplatform 100 has all of the components, software, and power supplyneeded to operate independently of any other systems. In thisillustrative, but nonlimiting, embodiment, nothing is required to beattached or integrated with the transportable private cloud computingplatform 100 in order for it to instantiate a private cloud. Aninput/output device for use by a system administrator may be built intothe transportable private cloud computing platform 100. A power supplyor a power generation means may be built into the transportable privatecloud computing platform 100. FIG. 7 illustrates a transportable privatecloud computing platform 100 with a built in keyboard, monitor, andmouse 701 and a battery pack 702.

In an illustrative, but nonlimiting, embodiment, the transportableprivate cloud computing platform 100 has a removably attached mobilitymechanism to allow for ease of mobility. An illustrative, butnonlimiting, embodiment of the mobility mechanism is shown in FIG. 8.The removably attached mobility mechanism, as shown in FIG. 8, is a setof four (4) wheels 801. The removably attached mobility mechanism couldbe in the form of four wheels 801, rollers, a tri-track chassis, anamphibious hull, or any other mechanism that will allow thetransportable private cloud computing platform 100 to be moved withoutlifting.

In a illustrative, but nonlimiting, embodiment, the transportableprivate cloud computing platform 100 has a resizable removably attachedtransit case 108, allowing for a larger or additional at least one rack101. FIG. 9 illustrates a modular transportable private cloud computingplatform 204 with an additional rack added. The advantage of having aresizable removably attached transit case 108 is to allow for easyscalability as computing needs change.

In an illustrative, but nonlimiting, embodiment, there is more than oneprivate cloud instance running on a single transportable private cloudcomputing platform 100. It is envisioned that several of the embodimentsillustrated in FIG. 2 will have more than one rack to form the at leastone rack 101 of the single transportable private cloud computingplatform 100, and each rack will have all the components and/or devicesnecessary to instantiate a separate private cloud instance. Shown inFIG. 10, a mobile transportable private cloud computing platform 205 isa transportable private cloud computing platform 100 running two privatecloud instances 1001.

In another illustrative, but nonlimiting, embodiment, more than onetransportable private cloud computing platform 100 may be joined tocreate a single private cloud instance. In FIG. 10, two racktransportable private cloud computing platforms 202 are joined to createa single private cloud instance 1002.

In an illustrative, but nonlimiting, embodiment, the transportableprivate cloud computing platform 100 creates and maintains a wirelessnetwork. As shown in FIG. 11, a ruggedized transportable private cloudcomputing platform 203 has been deployed and maintains a secure wirelessnetwork 1101 to enable users to connect from anywhere within the rangeof the wireless network. It is envisioned that an antenna may beattached to a transportable private cloud computing platform 100 foradditional range.

In an illustrative, but nonlimiting, embodiment, the transportableprivate cloud computing platform 100 is connected to a public orcommunity cloud. The connection is limited so that the transportableprivate cloud computing platform 100 may exchange data with the publicor community cloud, but is not part of the public or community cloud. InFIG. 11, a ruggedized transportable private cloud computing platform 203has been deployed and is connected to a public cloud 1102 in order toquery a database 1103 in the public cloud.

In order to be operational, the transportable private cloud computingplatform 100 must have software installed to enable it to perform thefunctions of instantiating a private cloud, migrating softwareapplications to the cloud, and managing cloud resources. FIG. 12 is atable of representative software components. Most, if not all, of thesesoftware components may be current off-the-shelf software (COTS). Thegraphical user interface (GUI) 1201 is a software component that, amongother things, allows the system administrator to interact with thetransportable private cloud computing platform 100. VMware vSphere 1202is a software component that, among other things, allows a systemadministrator to create a private cloud instance. VMware vDirector 1203is a software component that, among other things, allows a systemadministrator to manage infrastructure-as-a-service from the cloud.VMware vCenter 1204 is a software component that, among other things,allows a system administrator to manage virtualizations in the cloud. CAAppLogic 1205 is a software component that, among other things, allows asystem administrator to integrate, monitor, and scale softwareapplications and cloud infrastructure. EM7 System Management 1206 is asoftware component that, among other things, allows for cloud resourcemonitoring. Ni2 1207 is a software component that, among other things,allows the system administrator to build and maintain an inventory ofall cloud physical and virtual resources. CA RSI 1208 is a softwarecomponent that, among other things, implements user authentication. Notall of these software components are necessary to operate thetransportable private cloud computing platform 100. The transportableprivate cloud computing platform 100 needs to have a GUI, and softwareto enable a system administrator to instantiate a private cloud.

The methods of initializing the transportable private cloud computingplatform 100 and migrating software applications to the transportableprivate cloud computing platform 100 will now be discussed withreference to the flowcharts in FIG. 13 and FIG. 14, respectively. In thedescription of the flowcharts, the functional explanation marked withnumerals in angle brackets, <nnn>, will refer to the flowchart blocksbearing that number.

A feature of the transportable private cloud computing platform 100 isthat the interface device 105 provides step-by-step guidance to enable anovice system administrator with no cloud technical experience to createa fully configured and operational private cloud, administer the cloud,allocate virtual servers and manage the private cloud. The method ofinitializing the transportable private cloud computing platform 100 isshown in FIG. 13. The process starts <1301> when the systemadministrator applies power to a power supply circuit 107 of thetransportable private cloud computing platform 100 <1302>, whichactivates the graphical user interface (GUI) 1201 of the interfacedevice 105 <1303>. The graphical user interface (GUI) 1201 presents thesystem administrator with a choice of cloud operating system and queriesthe system administrator for a choice <1304>. Once the systemadministrator chooses a cloud operating system <1305>, the operatingsystem is started <1306> to create a private cloud instance.

The graphical user interface (GUI) 1201 then prompts the systemadministrator to input required keys <1307>, and the cloud operatingsystem virtualizer is initiated <1308>. The graphical user interface(GUI) 1201 then prompts the system administrator to enter the IP rangeof the plurality of servers 102 <1309>, and the cloud operating systemfinds each of the plurality of servers 102 and initializes with theselected cloud computing operating system <1310>, if it hasn't alreadybeen initialized. The physical resources of each server of the pluralityof servers 102 is then incorporated into the private cloud <1311>. Thegraphical user interface (GUI) 1201 then prompts the systemadministrator to provide virtual server information <1312>, and thecloud operating system creates the virtual servers <1313>. Once thevirtual servers have been created, the method of initializing thetransportable private cloud computing platform 100 is complete <1314>.

In an illustrative, but nonlimiting, embodiment of the method ofinitializing the transportable private cloud computing platform 100, thesystem administrator is required to authenticate after the graphicaluser interface (GUI) 1201 of the interface device 105 is activated. Thesystem administrator must provide valid credentials before the graphicaluser interface (GUI) 1201 will present the system administrator with achoice of cloud operating systems.

In an illustrative, but nonlimiting, embodiment of the method ofinitializing the transportable private cloud computing platform 100, thesystem administrator is presented with a list of IP addresses, each ofthe IP addresses representing one of the plurality of servers, to beintegrated into the private cloud.

In an illustrative, but nonlimiting, embodiment of the method ofinitializing the transportable private cloud computing platform 100, thesystem administrator is allowed to manually add or remove availabletransportable private cloud computing platform resources.

A feature of the transportable private cloud computing platform 100 isthat the interface device 105 provides step-by-step automated assistancea novice system administrator in the execution of an automatedassessment of a target physical server with running softwareapplications to determine what configuration a virtual server will needto run the software application, establish a correctly configuredvirtual server instance, and migrate the physical server application tothe virtual server instance. It is envisioned that the method ofmigrating software applications to the transportable private cloudcomputing platform 100 may be performed at any time after thetransportable private cloud computing platform 100 has been initialized.

The method of migrating software applications to the transportableprivate cloud computing platform 100 is shown in FIG. 14. The processstarts <1401> when a system administrator utilizes the interface device105 to invoke a software application migration system. The softwareapplication migration system is normally built into the graphical userinterface (GUI) 1201, as part of the interface device 105, but it couldbe embodied in commercial off-the-shelf (COTS) software. The softwareapplication migration system offers software application migrationoptions to the system administrator <1402>. The system administrator isguided by the software application migration system to search forsoftware applications that are available to be migrated to thetransportable private cloud computing platform 100. In particular, thesystem administrator may identify the IP address of a server to beevaluated <1403> for software applications to migrate.

However, the software application migration system may automaticallysearch for and select a server for evaluation. Once the server has beenidentified, the software application migration system searches forsoftware applications that are candidates for migration <1404>. Thesoftware application migration system evaluates each of these candidatesfor migration <1405>, and additional information may be queried from thesystem administrator <1406> to facilitate the evaluation process. Thesoftware application migration system presents a list of softwareapplications that are available to be migrated <1407>, and the systemadministrator selects a software application from the list to bemigrated to the transportable private cloud computing platform 100<1408>. Once a software application is selected by the systemadministrator, the software application migration system resources thecorrect virtual server configuration <1409> on the transportable privatecloud computing platform 100 to accommodate the migrating softwareapplication. The software application migration system then migrates themigrating software application to the transportable private cloudcomputing platform 100 <1410>. Finally, any software application data ofthe migrating software application is also migrated to the transportableprivate cloud computing platform 100 <1411>. This process may berepeated if there are more software applications to be migrated from thesame server <1414>. In addition, this process may be repeated if thereare more servers to evaluate for software applications to migrate<1415>. Once all desired servers have been evaluated and all desiredsoftware applications have been migrated from those servers, the methodof migrating software applications to the transportable private cloudcomputing platform 100 is complete <1416>.

In an illustrative, but nonlimiting, embodiment, the final step is atest of the network connectivity <1412>, migrating software application,and any migrating software application data <1413>, before migration iscomplete. In another illustrative, but nonlimiting, embodiment, thesoftware application migration system is fully automated and does notrequire human interaction with the interface device 105.

The method of initializing the transportable private cloud computingplatform 100 and method of migrating software applications to thetransportable private cloud computing platform 100 may be performed insequence, as shown in FIG. 15. In FIG. 15, the method of initializingthe transportable private cloud computing platform 100 is performedfirst, followed immediately by the method of migrating softwareapplications to the transportable private cloud computing platform 100.

In an illustrative, but nonlimiting, embodiment as shown in FIG. 15, themethod of initializing the transportable private cloud computingplatform 100 and method of migrating software applications to thetransportable private cloud computing platform 100 are performed insequence. The combined sequential process starts <1501> when the systemadministrator applies power to a power supply circuit 107 of thetransportable private cloud computing platform 100 <1502>, whichactivates the graphical user interface (GUI) 1201 of the interfacedevice 105 <1503>. After the graphical user interface (GUI) 1201 of theinterface device 105 is activated, the system administrator is promptedfor a user ID and password <1504> for authentication. Once the systemadministrator enters a valid user ID and password, the systemadministrator is logged onto the graphical user interface (GUI) 1201<1505>.

After the system administrator has logged onto the graphical userinterface (GUI) 1201, the graphical user interface (GUI) 1201 presentsthe system administrator with a choice of cloud operating system andqueries the system administrator for a choice <1506>. Once the systemadministrator chooses a cloud operating system <1507>, the operatingsystem is started <1508> to create a private cloud instance.

The graphical user interface (GUI) 1201 then prompts the systemadministrator to input required keys <1509>, and the cloud operatingsystem virtualizer is initiated <1510>. The graphical user interface(GUI) 1201 then prompts the system administrator to enter the IP rangeof the plurality of servers 102 <1511>, and the cloud operating systemfinds each of the plurality of servers 102 and initializes with theselected cloud computing operating system <1512>, if it hasn't alreadybeen initialized. The physical resources of each server of the pluralityof servers 102 is then incorporated into the private cloud <1513>. Thegraphical user interface (GUI) 1201 then prompts the systemadministrator to provide virtual server information <1514>, and thecloud operating system creates the virtual servers <1515>. Once thevirtual servers have been created, the method of initializing thetransportable private cloud computing platform 100 is complete.

The system administrator may choose to immediately execute the method ofmigrating software applications to the transportable private cloudcomputing platform 100 after initialization. The second part of thecombined sequential process shown in FIG. 15 begins when the systemadministrator utilizes the graphical user interface (GUI) 1201 to launchthe application migration system. The software application migrationsystem offers software application migration options to the systemadministrator <1516>. The system administrator is guided by the softwareapplication migration system to search for software applications thatare available to be migrated to the transportable private cloudcomputing platform 100. In particular, the system administrator mayidentify the IP address of a server to be evaluated <1517> for softwareapplications to migrate.

Once the server has been identified, the software application migrationsystem searches for software applications that are candidates formigration <1518>. The software application migration system evaluateseach of these candidates for migration <1519>, and additionalinformation may be queried from the system administrator <1520> tofacilitate the evaluation process. The software application migrationsystem presents a list of software applications that are available to bemigrated <1521>, and the system administrator selects a softwareapplication from the list to be migrated to the transportable privatecloud computing platform 100 <1522>. Once a software application isselected by the system administrator, the software application migrationsystem resources the correct virtual server configuration <1523> on thetransportable private cloud computing platform 100 to accommodate themigrating software application. The software application migrationsystem then migrates the migrating software application to thetransportable private cloud computing platform 100 <1524>. Any softwareapplication data of the migrating software application is also migratedto the transportable private cloud computing platform 100 <1525>. Thecorrect network connectivity is created <1526>. A test is conducted ofthe migrating software application, any migrating software applicationdata, and the network <1527>, before migration is complete.

The graphical user interface (GUI) 1201 then presents a list ofremaining applications that are candidates for migration <1528>. If thesystem administrator desires to migrate more applications from the listof available candidates <1529>, he selects them from the list <1522> andthe process continues as described above. If the system administratordecides not to migrate more applications or if there are no moreavailable candidate applications for migration <1529>, the method ofmigrating software applications to the transportable private cloudcomputing platform 100 is complete.

Finally, the graphical user interface (GUI) 1201 will present the systemadministrator with the option of starting a system managementapplication <1530>. If the system administrator chooses to start thesystem management application <1531>, the system management applicationis initiated <1532>. The graphical user interface (GUI) 1201 is thensent to the background waiting to be summoned <1533>. When summoned, thegraphical user interface (GUI) 1201 will present to the systemadministrator the options of launching the application migration systemor launching the system management application <1534>. When the systemadministrator is finished migrating applications and adjusting physicalresources, the combined sequential process is complete <1535>.

OPERATIONAL EXAMPLE 1

In an operation example of the transportable private cloud computingplatform 100, a mobile transportable private cloud computing platform205 is deployed at a coastal city by the Federal Emergency ManagementAgency (FEMA) the prior to the arrival of a major hurricane. In thisexample, the transportable private cloud computing platform 100 has aportable generator and fuel supply loaded on the trailer in addition tothe racks, servers, and other equipment. As the city evacuates inadvance of the arrival of the hurricane, a FEMA employee with littletraining in the field of cloud computing initializes the mobiletransportable private cloud computing platform 205 by following theguidance of the interface device 105. Once the FEMA employee creates aprivate cloud instance on the mobile transportable private cloudcomputing platform 205, he is able to utilize the software applicationmigration system to migrate software applications and data from the FEMAcommand center. At this point, the mobile transportable private cloudcomputing platform 205 is operating as a redundant system, capable ofserving as a fail-over system should the FEMA command center becomeinoperable. The mobile transportable private cloud computing platform205 creates a wireless network, so it operates as a stand-alone unit.

Just prior to the arrival of the hurricane, the mobile transportableprivate cloud computing platform 205 is relocated to a safe location outof the path of the hurricane. As the mobile transportable private cloudcomputing platform 205 moves down the highway, it is fully operationalbecause it has an internal power supply and is connected to the FEMAcommand center through the wireless network. When the hurricane strikesthe coastal city, the FEMA command center may rely on the mobiletransportable private cloud computing platform 205 as a backup system.

OPERATIONAL EXAMPLE 2

In an operation example of the transportable private cloud computingplatform 100, a ruggedized transportable private cloud computingplatform 203 is deployed in a remote location by the U.S. Army. In thisexample, the remote location has no direct connection to the Internetand has intermittent and unreliable satellite access. The ruggedizedtransportable private cloud computing platform 203 is transported to theremote location on a HMMWV. Once on site, a soldier with little trainingin the field of cloud computing initializes the ruggedized transportableprivate cloud computing platform 205 by following the guidance of theinterface device 105.

Once the soldier creates a secure private cloud instance on theruggedized transportable private cloud computing platform 205, he isable to utilize the software application migration system to migratesoftware applications and data to the ruggedized transportable privatecloud computing platform 205 to create a tactical operations center. Theruggedized transportable private cloud computing platform 205 alsocreates and maintains a secure wireless network, so small hand-held andvehicle-mounted computer systems within range of the secure wirelessnetwork are able to exchange data and interact with the ruggedizedtransportable private cloud computing platform 205. An antenna could beattached to the ruggedized transportable private cloud computingplatform 205 to provide more range for the wireless network.

OPERATIONAL EXAMPLE 3

In an operational example of the transportable private cloud computingplatform 100, a modular transportable private cloud computing platform204 is deployed in a parking space by the IT staff of a hospital. Inthis example, the IT staff is preparing to move all the hospital serversand computer equipment from a server room inside the hospital to a datacenter in a building adjoining the hospital. The hospital does not havethe server capacity to move the servers piecemeal, and it does not havethe budget to buy additional servers to facilitate the move. The modulartransportable private cloud computing platform 204 is rented for a shorttime to enable the hospital to complete the relocation of its ITdepartment and servers.

In this example, a member of the hospital IT staff with little trainingin the field of cloud computing initializes the modular transportableprivate cloud computing platform 204 by following the guidance of theinterface device 105. Once the IT staff creates a private cloud instanceon the modular transportable private cloud computing platform 204, he isable to utilize the software application migration system to migratesoftware applications and data from the hospital server room to themodular transportable private cloud computing platform 204. Softwareapplications and data are hosted on the modular transportable privatecloud computing platform 204 and the hospital IT systems continue tooperate as the IT staff relocates equipment to the data center. Once thedata center is operational, software applications and data aretransferred from the modular transportable private cloud computingplatform 204 to the data center and the modular transportable privatecloud computing platform 204 is taken out of operation.

Furthermore, it should be understood that when introducing elements ofthe present invention in the claims or in the above description of theillustrative, but nonlimiting, embodiment of the invention, the terms“have,” “having,” “includes” and “including” and similar terms as usedin the foregoing specification are used in the sense of “optional” or“may include” and not as “required.” Similarly, the term “portion”should be construed as meaning some or all of the item or element thatit qualifies.

Thus, there have been shown and described several embodiments of a novelinvention. As is evident from the foregoing description, certain aspectsof the present invention are not limited by the particular details ofthe examples illustrated herein, and it is therefore contemplated thatother modifications and applications, or equivalents thereof, will occurto those skilled in the art. Many changes, modifications, variations andother uses and applications of the present construction will, however,become apparent to those skilled in the art after considering thespecification and the accompanying drawings. All such changes,modifications, variations and other uses and applications which do notdepart from the spirit and scope of the invention are deemed to becovered by the invention which is limited only by the claims thatfollow.

What is claimed is:
 1. A method of initializing a transportable privatecloud computing platform, the method comprising: applying power to apower supply circuit of a transportable private cloud computingplatform, which also includes a rack, an interface device, a pluralityof servers, at least one cloud computing operating system, and at leastone network switch; activating a graphical user interface on theinterface device; utilizing the interface device to provide queries to asystem administrator so that a particular cloud computing operatingsystem may be selected from the at least one cloud computing operatingsystems; starting the selected cloud computing operating system thatoperates as a private cloud; utilizing the interface device to requestrequired keys from a system administrator; initiating a cloud operatingsystem virtualizer; utilizing the interface device to allow the systemadministrator to enter a IP range of addresses, each of the IP addressesrepresenting one of the plurality of servers, to be integrated into theprivate cloud; locating and initializing, if not already initialized,each system administrator-selected server with the selected cloudcomputing operating system; incorporating physical resources of eachserver of the plurality of servers into the private cloud; utilizing theinterface device to provide queries to the system administrator so thatvirtual server information is entered; and creating the virtual servers.2. The method of claim 1, wherein the system administrator authenticateswith the transportable private cloud computing platform.
 3. The methodof claim 1, wherein the system administrator is presented with a list ofIP addresses, each of the IP addresses representing one of the pluralityof servers, to be integrated into the private cloud.
 4. The method ofclaim 1, wherein the interface device allows the system administrator toadd or remove available transportable private cloud computing platformresources.
 5. The method of claim 1, further comprising housing thepower supply circuit, the rack, the interface device, the plurality ofservers, the at least one cloud computing operating system and the atleast one network switch in a transit case.
 6. The method of claim 1,further comprising housing the power supply circuit, the rack, theinterface device, the plurality of servers, the at least one cloudcomputing operating system and the at least one network switch in amobile transit case.
 7. The method of claim 1, further comprisinghousing the power supply circuit, the rack, the interface device, theplurality of servers, the at least one cloud computing operating systemand the at least one network switch in a resizeable transit case.
 8. Themethod of claim 1, further comprising housing the power supply circuit,the rack, the interface device, the plurality of servers, the at leastone cloud computing operating system and the at least one network switchin a hardened transit case.
 9. The method of claim 1, further comprisinghousing the power supply circuit, the rack, the interface device, theplurality of servers, the at least one cloud computing operating systemand the at least one network switch in a ruggedized transit case. 10.The method of claim 1, wherein the interface device includes at leastone of a keyboard, a video display, a mouse (KVM) switch, and agraphical user interface.